Repository navigation
Conversation
Release images now carry an SPDX SBOM attestation next to the provenance attestation build-push-action already adds. Marking a release stable retags the image that release published instead of rebuilding it. The rebuild paired an older wheel with the default branch's Dockerfile, and gave users who had already pulled the release new layers to download. imagetools create carries the attestation manifests across. docs/ci-cd.md gains a Docker image section: what the image contains, how to persist the reachability engine cache between container runs, keeping pulls cheap in CI, and how to inspect the attestations.
This was referenced Nov 4, 2026
Contributor
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 5e0a92a. Configure here.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three small changes to how the Docker image is published and documented. Nothing in the package or the image's contents changes.
Changes
release.ymlsetssbom: trueondocker/build-push-action, so each release image carries an SPDX SBOM next to the provenance attestation the action already adds. It is generated from the built image on every build. Toolchains installed from release archives rather than a package manager (Rust via rustup, PyPy) show up thinly or not at all, and the docs say so.stableis a retag.docker-stable.ymlused to rebuild the image from the default branch withCLI_VERSION=<version>. That paired an older wheel with whatever the Dockerfile was at the time, and gave users who had already pulled<version>new layers to download. It now pointssocketdev/cli:stableat the publishedsocketdev/cli:<version>withdocker buildx imagetools create, after validating the input and checking that the tag exists. A--dry-runagainst2.11.11confirms that the retag keeps both attestation manifests.docs/ci-cd.mdcovers what the image contains, how to persist the reachability engine cache between container runs (a fresh container otherwise downloads the engine on every--reachrun), how to keep image pulls cheap in CI, and how to inspect the provenance and SBOM.Verification
zizmor: no findings on either workflow.actionlint: only pre-existing findings (shellcheck info inrelease.yml, and it doesn't yet recognize the$/action syntax).imagetools create --dry-run -t … socketdev/cli:2.11.11produced an index with both platform manifests and bothattestation-manifestentries.Bumps to
2.11.12. #439 also targets2.11.12; whichever merges second rides that version and only needs the changelog merged.Ref: CE-433
🤖 Generated with Claude Code
Note
Low Risk
Changes are limited to CI workflows, documentation, and version metadata; runtime CLI behavior and image contents are unchanged aside from new attestations on future release builds.
Overview
Release Docker builds now publish an SPDX SBOM attestation alongside provenance by setting
sbom: trueondocker/build-push-actioninrelease.yml.The manual stable workflow no longer rebuilds from PyPI/Dockerfile. It validates the release version, confirms
socketdev/cli:<version>exists on Docker Hub, and usesdocker buildx imagetools createto pointsocketdev/cli:stableat that image so stable matches the release digest and keeps its attestations. QEMU is disabled in setup because nothing is built.Docs add a Docker image section in
docs/ci-cd.md(usage, reachability engine cache mounts, CI pull tips, inspecting provenance/SBOM). Version is bumped to 2.11.12 with matching changelog entries.Reviewed by Cursor Bugbot for commit 5e0a92a. Configure here.